RESUME OF RADIO RESOURCE CONTROL WITHOUT CONTEXT SEARCH

专利摘要:
according to some modalities, a target network node to communicate with user equipment (eu) that was previously in communication with a source network node, comprises an interface operably coupled to a set of processing circuits. the interface is configured to receive a resume connection request from the user equipment, where the resume connection request comprises a resume identification associated with the source network node. the processing circuitry is configured to determine that the eu was previously in communication with the source network node. the interface is further configured to transmit the request to resume connection to the source network node, receive a radio resource control response (rrc) from the source network node, and forward the rrc response to the eu.
公开号:BR112019015723A2
申请号:R112019015723-9
申请日:2017-12-27
公开日:2020-03-24
发明作者:Rugeland Patrik；L. J. DA SILVA Icaro；Mildh Gunnar
申请人:Telefonaktiebolaget Lm Ericsson (Publ)；
IPC主号:

专利说明:

RESUME OF RADIO RESOURCE CONTROL WITHOUT CONTEXT SEARCH
FIELD OF TECHNIQUE [001] The present invention relates, in general, to wireless communications and, more particularly, to wireless communications without relocating EU context information.
BACKGROUND [002] In the Third Generation Partnership Project (3GPP) Next Generation New Radio Access Technology (NR) study item, it is proposed that the Radio Resource Control (RRC) state model should be extended from 2 states (RRC IDLE and RRC CONNECTED) to 3 states (adding new RRCINACTIVE state). A similar state model is also considered for Long Term Evolution (LTE) when LTE is connected to the Next Generation Core Network (also known as 5GCN).
[003] One aspect of the RRC INACTIVE status is that the User Equipment (UE) and the Radio Access Network (RAN) store the context of the Access Stratum (AS), and that the CN / RAN interface (called SI in LTE / Evolved Packet Core (EPC) and NG-C in NR and LTE when connected to 5G-CN) is maintained. This means that when a UE needs to reconnect to the network, it can resume an old connection, which can be much faster than defining a new connection.
[004] FIGURE 1 illustrates an exemplary high-level next-generation network architecture; In FIGURE 1, the LTE eNB and NR BS nodes of RAN (also called a gNB) are connected to the Next Generation CN (NG-CN or 5G-CN) using the NG-C control interface and NG user plan interface -U. GNB has functionality similar to LTE eNB.
Petition 870190073105, of 07/30/2019, p. 190/269
2/50 [005] FIGURE 2 illustrates proposed state transitions for NR. The proposed procedures for transitioning between states can be found at R2-1700535. In certain potential scenarios, even if the UE has stored the context in RRCINACTIVE, the RAN can, at any time, discard the context and the CN / RAN connection when the UE is in RRC INACTIVE. In the event that the RAN has dropped the context, the RAN will inform the UE of this when the UE sends an RRCConnectionResumeRequest message by replying with an RRCConnectionSetup message instead of an RRCConnectionResume message. In this case, the UE will also drop the context and continue to define the RRC connection with the message from RRCConnectionSetupComplete.
[006] In scenarios where the AS context is stored and the CN / RAN connection is maintained, the CN is unaware that the UE is in RRCINACTIVE and will consider the UE to be in ECM_CONNECTED (or the state of NR CN equivalent). This means that the CN will not perform radiolocation of the UE when the incoming downlink (DL) packet (s) arrive, instead, the CN will send the packets via NG-U to the RAN, and the RAN node will start radiolocation (or notification) if necessary.
RAN-based Notification Area [007] Another aspect of the RRC INACTIVE status is the proposal for a RAN-based notification area. Some of the assumptions of 3GPP RAN2 related to the RAN-based notification area are:
1. RAN2 assumes that the UE performs a CN level location update when crossing a TA boundary when inactive (in addition to RAN updates based on RAN areas).
2. There will be diffusion of the Localization Code of CN / NG Nucleus
Petition 870190073105, of 07/30/2019, p. 191/269
3/50 (similar to Tracking Area code) in a company's system information
NR cell.
1. RAN-based notification area is EU specific and configurable by gNB via dedicated signaling
There will be a unique global Cell ID broadcast in NR Cell system information.
For the inactive state, there will be a way to configure the UE with a RAN-based notification area that is less than a TA.
A RAN notification area can cover a single cell or multi-cell [008] The RAN-based notification area - the RAN area - allows the UE to move freely within the area without informing the network. When the UE wants to transmit data, it must be able to resume its connection. In this way, even if the UE can move freely within the RAN area, it will still be tracked by the CN within the Tracking Areas (TA) as the UE is expected to perform TA updates to the CN due to mobility . To manipulate the RAN areas, the UE will also perform RAN area updates.
Suspension & Resume Procedures for the RRC_INACTIVE State [009] The proposed Suspension and Resume Procedures for the new RRC RRC INACTIVE status are illustrated in FIGURES 3 and 4.
[0010] FIGURE 3 illustrates a proposed procedure for a successful RRC Connection Suspension. In the example of FIGURE 3, the UE is shown initially in the RRC CONNECTED state. User data is exchanged between
Petition 870190073105, of 07/30/2019, p. 192/269
4/50 the UE and the NR gNB. In step 1, the NR gNB sends an RRC Connection Suspension message to the UE. The UE enters the RRCJNACTIVE state.
[0011] FIGURE 4 illustrates a proposed procedure for a successful RRC Connection Resumption. In the example in FIGURE 4, the UE is shown initially in the RRCJNACTIVE state. The NR gNB sends a radiolocation message to the UE. The UE performs the acquisition of Access Information. In step 1, the UE sends a Physical Random Access Channel (PRACH) preamble to NR gNB. In step 2, the NR gNB sends a Random Access Response (RAR) to the UE. In step 3, the UE sends a RRC Connection Resume Request message to NR gNB. In step 4, the NR gNB sends a RRC Connection Resume message to the UE. The UE enters the RRC_CONNECTED state. In step 5, the UE sends a RRC Connection Resume Completion message to NR gNB. User data is exchanged between the UE and the NR gNB.
[0012] During the two RRC Connection Suspension and RRC Connection Resume procedures, the CN / RAN connection between the gNB and the Next Generation CN is maintained (which means that NR gNB - CN signaling is not required ).
[0013] Notably, in the previous discussion, since the UE can move within the RAN area while in RRCJNACTIVE without informing the network, if it resumes its connection in another gNB other than the one in which it was suspended, the target gNB has to seek the UE context from the source gNB.
SUMMARY [0014] To solve the foregoing problems, a method on a target network node for communicating with user equipment is described
Petition 870190073105, of 07/30/2019, p. 193/269
5/50 (UE) that was previously in communication with a source network node. The method includes receiving a resume connection request from a UE, the resume connection request comprises a resume identification associated with the source network node; transmit the request to resume connection to the source network node; receive a radio resource control (RRC) response from the source network node; and forward the RRC response to the UE.
[0015] A target network node for communicating with user equipment (UE) that was previously in communication with a source network node is also described. The target network node includes an interface operably coupled to the set of processing circuits. The interface is configured to receive a connection resume request from the UE, where the connection resume request comprises a resume identification associated with the source network node. The processing circuitry is configured to determine that the UE (110) was previously in communication with the source network node. The interface is additionally configured to transmit the request to resume connection to the source network node; receive a radio resource control (RRC) response from the source network node; and forward the RRC response to the UE.
[0016] In some embodiments, the target network node is a gNB and the source network node is a gNB.
[0017] In some modalities, the request to resume connection is an RRCConnectionResumeRequest. In some embodiments, the request to resume connection comprises a security token. In some embodiments, the request to resume connection has integrity protected with the use of a security key used during previous communications with the source network node. In some modalities, small data
Petition 870190073105, of 07/30/2019, p. 194/269
6/50 received as part of or in conjunction with the request to resume connection. In some embodiments, the request to resume connection is transmitted to the source network node as part of or in conjunction with a recovery UE context request.
[0018] In some modalities, the RRC response is an RRCConnectionSuspend. In some modalities, the RRC response comprises one or more of: a new resume identification associated with the source network node; a new security parameter; and a radio access network (RAN) allocation.
[0019] In certain modalities, the method also comprises, receiving through the interface, a UE context response from the source network node.
[0020] In certain modalities, the method also includes creating, through the set of processing circuits, a local UE context; suspend the UE; and release the local EU context.
[0021] A method on a source network node to facilitate communications between user equipment (UE) and a target network node is also described. The method includes receiving a request to resume connection to the UE from the target network node, the request to resume connection including a resume identification associated with the source network node. The method also includes verifying the request to resume connection to the UE; generate a radio resource control (RRC) response for the UE; and transmitting the RRC response to the UE through the target network node.
[0022] A source network node is also described to facilitate communications between user equipment (UE) and a target network node. The source network node comprises an operably coupled interface,
Petition 870190073105, of 07/30/2019, p. 195/269
7/50 to the set of processing circuits. The interface is configured to receive a resume connection request to the UE from the target network node, the resume connection request including a resume identification associated with the source network node. The processing circuitry is configured to verify the request to resume connection to the UE and generate a radio resource control (RRC) response to the UE. The interface is further configured to transmit the RRC response to the UE through the target network node.
[0023] In some embodiments, the target network node is a gNB and the source network node is a gNB.
[0024] In some modalities, the request to resume connection is an RRCConnectionResumeRequest. In some embodiments, the request to resume connection comprises a security token. In some embodiments, the request to resume connection has integrity protected with the use of a security key used during previous communications with the UE. In some embodiments, small data is received as part of or in conjunction with the request to resume connection. In some embodiments, the request to resume connection is transmitted to the source network node as part of or in conjunction with a recovery UE context request.
[0025] In some modalities, the RRC response is an RRCConnectionSuspend. In some modalities, the RRC response comprises one or more of: a new resume identification associated with the source network node; a new security parameter; and a radio access network (RAN) allocation.
[0026] In some modalities, the method comprises receiving, for
Petition 870190073105, of 07/30/2019, p. 196/269
8/50 through the interface, the request to resume connection to the target network node as part of a recovery user equipment (UE) context request. In some embodiments, the method comprises transmitting, through the interface, a UE context response to the target network node. In some embodiments, the method includes assigning, through the set of processing circuits, a return identification to the UE, the return identification is associated with the source network node.
[0027] A method on a user device (UE) for communicating with a target network node is also described. The method includes transmitting a resume connection request to the target network node, the resume connection request including a resume identification associated with a source network node previously communicating with the UE. The method further comprises receiving a radio resource control (RRC) response that originates from the source network node and is forwarded to the UE by the target network node.
[0028] User equipment (UE) for communication with a target network node is also described. The UE includes an interface operably coupled to the processing circuitry. The processing circuitry is configured to operate in an RRCINACTIVE state. The interface is configured to transmit a request to resume connection to the target network node, the request to resume connection includes a resume identification associated with a source network node previously communicating with the UE; and receiving a radio resource control (RRC) response that originates from the source network node and is forwarded to the UE by the target network node.
[0029] In some modalities, the method also includes obtaining the
Petition 870190073105, of 07/30/2019, p. 197/269
9/50 resume identification associated with the source network node. In some embodiments, the target network node is a gNB and the source network node is a gNB.
[0030] In some modalities, the RRC response is an RRCConnectionSuspend. In some modalities, the request to resume connection is an RRCConnectionResumeRequest. In some embodiments, the request to resume connection comprises a security token. In some embodiments, the request to resume connection has integrity protected with the use of a security key used during previous communications with the source network node. In some embodiments, small data is transmitted as part of or in conjunction with the request to resume connection.
[0031] In some modalities, the RRC response comprises one or more of: a new resumption identification associated with the source network node; a new security parameter; and a radio access network (RAN) allocation.
[0032] Certain embodiments of the present invention can provide one or more technical advantages. For example, in certain modalities, the network does not reallocate the UE context when the UE resumes its connection. Since not all gNBs are connected with an equally good backhaul (for example, if implemented in a star-shaped layout), it may be advantageous to keep the UE context in the center of the star instead of relocating it to one end if the UE is only active for a short time. In addition, relocation of the context to a target eNB / gNB will require signaling both with the RAN and between RAN and CN. Allowing an UE to request that you resume your connection or perform an RAN / CN area update on a target gNB without reallocating the UE context to the target gNB can reduce the
Petition 870190073105, of 07/30/2019, p. 198/269
10/50 network congestion. Other advantages may be readily apparent to a person skilled in the art. Certain modalities may have all, some or none of the mentioned benefits.
BRIEF DESCRIPTION OF THE DRAWINGS [0033] For a more complete understanding of the modalities described and their characteristics and advantages, reference is now made to the following description, obtained in conjunction with the attached drawings, in which:
FIGURE 1 illustrates an exemplary high-level next-generation network architecture;
FIGURE 2 illustrates proposed state transitions for NR;
FIGURE 3 illustrates a proposed procedure for a successful RRC Connection Suspension;
FIGURE 4 illustrates a proposed procedure for a successful RRC Connection Resume;
FIGURE 5 illustrates an exemplary RRCINACTIVE to RRC CONNECTED resumption procedure, according to certain modalities;
FIGURE 6 illustrates a resumption of RRC connection to perform an update of the RAN area, according to certain modalities;
FIGURE 7 illustrates an exemplary NC Tracking Area (TA) update in RRC INACTIVE, according to certain modalities;
FIGURE 8 illustrates an example periodic RAN update in the old gNB, according to certain modalities;
FIGURE 9 illustrates an exemplary periodic update to the new gNB in an old RAN area, according to certain modalities;
FIGURE 10 illustrates an exemplary heterogeneous network implantation, according to certain modalities;
Petition 870190073105, of 07/30/2019, p. 199/269
11/50
FIGURE 11 illustrates an exemplary star-shaped implantation, according to certain modalities;
FIGURE 12 is a block diagram illustrating an embodiment of a network 100, according to certain embodiments;
FIGURE 13 illustrates an exemplary RRCConnection Resumption due to the periodic RAN area update in a new gNB without context relocation, according to certain modalities;
FIGURE 14 illustrates an example of small data transmission in RRCINACTIVE without relocation of UE context, according to certain modalities;
FIGURE 15 illustrates an exemplary state transition from RRC INACTIVE to RRC CONNECTED without relocation of context for small data transmission, according to certain modalities.
FIGURE 16 is a block diagram of an exemplary wireless device, according to certain modalities;
FIGURE 17 is a block diagram of an exemplary network node, according to certain modalities;
FIGURE 18 is a block diagram of an example radio network controller or core network node, according to certain modalities;
FIGURE 19 is a block diagram of an exemplary wireless device, according to certain modalities; and
FIGURE 20 is a block diagram of an exemplary network node, according to certain modalities.
DETAILED DESCRIPTION [0034] As described above, there are several technical issues involved
Petition 870190073105, of 07/30/2019, p. 200/269
12/50 in relocating user equipment (UE) context information to a new network node, particularly when the UE is, only briefly, in a state connected with the new network node. For example, if a UE is moving while on RRC_INACTIVE and resumes its connection on a different gNB, it may not be beneficial to always reallocate the UE context to the target gNB. This is especially true if the UE quickly suspends its connection back to RRCINACTIVE. A non-limiting example of such a scenario is when the UE is performing an update of the RAN or CN area record due to mobility. Another non-limiting example of such a scenario is when the UE is performing a periodic update of the RAN or CN area registration (for example, keep alive signaling). Yet another non-limiting example of such a scenario is when the UE has only little data to send / receive before it becomes inactive again. The problem can be particularly bad for rapidly changing UEs that are inactive, and will require frequent context reallocations.
[0035] The present invention contemplates several modalities that can solve these and other deficiencies associated with existing approaches. In some cases, this is achieved by enabling a UE RRC connection to be resumed shortly in a new gNB without reallocating the UE context and still guaranteeing security. Certain modalities describe a mechanism for how the UE can request to resume your connection (for example, from RRC INACTIVE to RRC CONNECTED) or perform an RAN / CN area update on a target gNB when the UE context is located in another gNB, without relocating the UE context to the target gNB. In certain modalities, instead of reallocating the EU context to gNB
Petition 870190073105, of 07/30/2019, p. 201/269
13/50 target, the gNB that contains the UE context communicates with the UE through the target gNB. Certain modalities also allow pre-population in the UE context for several potential target eNB / gNBs to accelerate the signaling transaction. In some cases, pre-population can also be done without removing the context in the source eNB / gNB.
RRC Connection Resume [0036] The baseline response for RRC resume is to reallocate the UE context to the target node where the UE sent the RRCConnectionResumeRequest message (also known as message 3 or msg3). This is due to the fact that, if the UE has been provided with a Next Hop Thread Counter (NCC), it can calculate the necessary security keys in order to protect msg3 integrity and have the ability to receive encrypted msg4 (RRCConnectionResume, RRCConnectionSuspend, or RRCConnectionSetup depending on whether the UE should resume a context, suspend for RRC_IINACTIVE, or if the context cannot be resumed - reconstruct the context).
[0037] Figure 5 illustrates an exemplary RRC INACTIVE to RRCCONNECTED resumption procedure. In particular, Figure 5 illustrates a successful resumption procedure. In the example in Figure 5, the new gNB sends a RRC (Resume ID, NCC) suspension to the UE. The UE enters the RRCINACTIVE state. In step 1, the UE sends a Random Access Preamble (RA) to the new gNB. In step 2, the new gNB sends a RAR to the UE. In step 3, the UE sends an RRCConnectionResumeRequest (Resume ID), with the integrity of the Packet Data Convergence Protocol (PDCP) protected to the new gNB. In some cases, data transmission occurs between the UE and the new gNB.
Petition 870190073105, of 07/30/2019, p. 202/269
14/50 [0038] In step 4, the new gNB sends a Recovery UE Context Request message to the old gNB. In step 5, the old gNB sends a Recovery UE Context Reply message to the new gNB. In step 6, the new gNB sends a Travel Switch Request to the AMF. In step 7, the AMF and UPF modify carriers. In step 8, the AMF sends a Commutation Confirmation (CONF) to the new gNB. In step 9, the new gNB sends an encrypted / integrity-protected RRCConnectionResume message from PDCP to the UE. The UE enters the RRC_CONNECTED state. In step 10, the UE sends an encrypted / integrity-protected RRCConnectionResumeComplete from PDCP to the new gNB.
[0039] In the example in Figure 5, calculating a new security key before message 3 (ie, step 3) makes it possible to reallocate the UE context since the new gNB / eNB should not be allowed to obtain the key old used in old gNB / eNB. It should also be mentioned, when the UE context is relocated, the CN / RAN connection will also be switched (SI for legacy EPC or NG for NextGenCore).
RAN Area Updates [0040] In certain scenarios, the network may know the location of UE in an RAN area level which can be, for example, a list of cells, a list of CN Tracking Areas, or a newly defined RAN area index. This means that when the UE moves out of the RAN area, it needs to inform the network. A proposed method for this is shown in Figure 6.
[0041] Figure 6 illustrates an RRC connection resumption to perform an RAN area update. In the example in Figure 7, the UE is
Petition 870190073105, of 07/30/2019, p. 203/269
15/50 initially in the RRC_INACTIVE state. The UE enters a new RAN area, and in step 1, it sends an RA preamble to the new gNB. In step 2, the new gNB sends a RAR message to the UE. In step 3, the UE sends an RRCConnectionResumeRequest message (resumelD, causeValue = ranNotificationAreaUpdateRequest) to the new gNB.
[0042] In step 4, the new gNB sends a Recovery UE Context Request message to the old gNB. In step 5, the old gNB sends a Recovery UE Context Reply message to the new gNB. In step 6, the new gNB sends a Commutation Request message to the AMF. In step 7, AMF and S-GW modify carriers. In step 8, the AMF sends a Confirmation of Commutation Request for Route Change to the new gNB. In step 9, the new gNB sends an RRCConnectionSuspend (ranArealnformation, NCC) message to the UE. The UE enters the RRCJNACTIVE state.
Tracking Area Update in RRC_INACTIVE [0043] In certain scenarios a UE must perform a CN Tracking Area update even in the RRCJNACTIVE state when the UE enters a TA that is not registered. An exemplary procedure for this is shown in Figure 7.
[0044] Figure 7 illustrates an exemplary NC Tracking Area update in the RRCJNACTIVE state. In the example in Figure 7, the UE is initially in the RRCJNACTIVE state. The UE enters a new TA. In step 1, the UE sends an RA preamble to the new gNB. In step 2, the new gNB sends a RAR message to the UE. In step 3, the UE sends an RRCConnectionResumeRequest message (resumelD, causValue = mo-signaling) to the new gNB. In step 4, the new gNB sends a Request for Information message
Petition 870190073105, of 07/30/2019, p. 204/269
16/50
UE Recovery context for old gNB. In step 5, the old gNB sends a Recovery UE Context Reply message to the new gNB. In step 6, the new gNB sends a RRCConnectionResume message to the UE. In step 7, the UE sends an RRCConnectionResumeComplete message (dedicatedinfoNAS = TAU Request) to the new gNB. The UE enters the RRC CONNECTED state.
[0045] In step 8, the new gNB sends a Request for commutation to the AMF. In step 9, AMF and S-GW modify carriers. In step 10, the AMF sends a Route Change Request CONF to the new gNB. In step 11, the new gNB sends a TAU request to the AMF. The AMF updates the Tracking Area. In step 12, the AMF sends a TAU Acceptance message to the UE. In step 13, the new gNB sends an EU Context Release message to the old gNB. During or after an inactivity timer expires, the new gNB sends an RRCConnectionSuspend (ranArealnformation, NCC) message to the UE. The UE enters the RRCINACTIVE state.
[0046] There are several assumptions for RAN-based notification, including:
1. RAN2 assumes that the UE performs a CN level location update when crossing a TA boundary when inactive (in addition to RAN updates based on RAN areas).
2. There will be diffusion of the CN / NG Core Location Area code (similar to the Tracking Area code) in system information of an NR Cell.
3. In RAN2, the UE will perform RRC signaling in order to carry out an NC update whenever it leaves its registered TA (as
Petition 870190073105, of 07/30/2019, p. 205/269
17/50 consequence of RRC signaling, RAN is aware of the UE location)
4. Support option 2 (cell list) and / or option 3 (RAN id) (FFS one of the two or both)
Periodic RAN Area Updates in RRC_INACTIVE [0047] In addition, in certain scenarios, the UE must perform periodic RAN area updates in RRC INACTIVE, similar to what is done for Periodic Updates of CN Tracking Area in the state RRC IDLE, so that the network has the ability, for example, to remove context from UEs that have been disconnected if an UE is unable to perform these periodic updates (once or multiple times, in LTE the default period for CN TAU is 54 minutes) . Since the UE should not perform CN TAU in RRCINACTIVE, it is necessary to make RAN area updates instead. If that fails, the RAN can report to the CN.
[0048] Since the UE performs periodic RAN area updates only if it is still in its old RAN area (otherwise it would have done a mobility-triggered RAN area update when it left the area), the UE you can return to the context in either the old gNB or a new gNB in the same area as shown in FIGURES 8 and 9 below, respectively.
[0049] FIGURE 8 illustrates an example periodic RAN update in the old gNB. In the example in Figure 8, the UE is initially in the RRC INACTIVE state. At the time or after an RAN area update timer expires, the UE, in step 1 sends an RA Preamble to the gNB. In step 2, gNB sends a RAR to the UE. In step 3, the UE sends an RRCConnectionResumeRequest message (resumeld, causeValue = ranNotificationAreaUpdateRequest) to gNB. In step 4, gNB
Petition 870190073105, of 07/30/2019, p. 206/269
18/50 sends a message from RRCConnectionSuspend (ranArealnformation, NCC) to the UE. The UE enters the RRCJNACTIVE state.
[0050] FIGURE 9 illustrates an exemplary periodic update on the new gNB in an old RAN area. In the example of FIGURE 9, the UE is initially in the RRCJNACTIVE state. At the time or after an RAN area timer expires, the UE in step 1 sends an RA Preamble to the new gNB. In step 2, the new gNB sends a RAR message to the UE. In step 3, the UE sends an RRCConnectionResumeRequestf summarizing Id, causeValue = ranNotificationAreaUpdateRequest) to the new gNB. In step 4, the new gNB sends a Recovery UE Context Request message to the old gNB. In step 5, the old gNB sends a Recovery UE Context Reply message to the new gNB. In step 6, the new gNB sends a Commutation Request message to the AMF. In step 7, AMF and S-GW modify carriers. In step 8, the AMF sends a Route Change Request CONF to the new gNB. In step 9, the new gNB sends an UE context release message to the old gNB. In step 10, the new gNB sends an RRCConnectionSuspend (ranArealnformation, NCC) message to the UE. The UE enters the RRCJNACTIVE state.
[0051] In the example in FIGURE 8 described above, the UE context does not have to be reallocated since the UE resumes the connection in the old gNB, while in the example in Figure 9, the UE context is reallocated.
Exemplary Configurations [0052] FIGURES 10 and 11 illustrate two exemplary implementations in which there are technical benefits in not relocating the UE context when the UE resumes its connection. Figure 10 illustrates a network implementation
Petition 870190073105, of 07/30/2019, p. 207/269
Exemplary heterogeneous 19/50, according to certain modalities. More particularly, Figure 10 illustrates a heterogeneous network implementation with a macrocell and 12 picocells. In the example in Figure 10, the RAN area consists of a macro gNB (with a wide coverage range) and 12 peak gNBs (with a much smaller coverage range). If a UE is connected to the Base macrostation when it suspended its connection and then moves while in the RRCINACTIVE state so that it enters the coverage of a picocell, when the UE resumes its connection, it will do this towards the picocell. If the UE has little or no data (for example, it only performs an RAN area update), in the baseline solution, the network will reallocate the UE context to the picocell and then quickly suspend the UE to RRC INACTIVE . If the UE moves again when in RRC INACTIVE, it can enter another picocell. When it then resumes its connection, the network will need to seek the context of the old picocell for the new picocell.
[0053] As described in more detail below, in certain modalities, the UE context can be maintained in the gNB macro. When the UE resumes the connection in picocell 1 and then suspends, the context is still in Macro gNB. When the UE then resumes the connection in picocell 2, the context will still be the same. In some modalities, an option is to duplicate / pre-allocate the UE context. For example, when the UE suspends its connection, the UE context is also stored in the gNB most likely to be resumed (for example, all nodes in the RAN area). Alternatively, the UE context can be stored in the gNB which the UE has further suspended the Macro gNB.
[0054] Figure 11 illustrates an exemplary star-shaped implementation, according to certain modalities. More
Petition 870190073105, of 07/30/2019, p. 208/269
20/50 particularly, Figure 11 illustrates an exemplary implementation with nine gNBs in the same RAN area, where the relocation of the UE context may not be ideal. The star-shaped implementation of Figure 11 includes a gNB in the center of the star, connected to eight gNBs located in the arms of the star where all gNBs are included in the RAN area. The other gNBs have no direct connection between them, but are connected via the central gNB. If the UE has its UE context stored in the central gNB when it is in the RRC INACTIVE state, and then move to one of the external gNB and perform the RRC connection resumption, if the UE context is sought for that gNB and the UE suspend back to RRCINACTIVE and then move to another gNB, the UE context will have to be reallocated again. In certain modalities, the UE context is stored in the central gNB and the UE resumes its context in any of the external gNBs, so that the context does not have to be relocated.
[0055] Figures 10 and 11 are just illustrations of exemplary implementations that can benefit from the modalities of the present invention. The various modalities described are especially advantageous for scenarios where the UE has very little data to send, or only sends, for example, RAN area updates. In some cases, if the UE has a large amount of data to transmit, the UE context can still be reallocated. Figures 12 to 20 provide further explanation of the modalities of the present invention.
Exemplary Network [0056] Figure 12 is a block diagram that illustrates a modality of a network 100, according to certain modalities. Network 100 includes one or more UE (s) 110 (which may alternately be called devices
Petition 870190073105, of 07/30/2019, p. 209/269
Wireless 21/50 110) and one or more network node (s) 115 (which may alternately be called NR gNBs 115 or eNBs). In certain embodiments, network nodes 115 can be differentiated as network nodes 115a, 115b, 115c. . . 115n. UEs 110 can communicate with network nodes 115 via a wireless interface. For example, an UE 110 can transmit wireless signals to one or more of network nodes 115 and / or receive wireless signals from one or more of network nodes 115. Wireless signals can contain voice traffic, traffic data, control signals and / or any other appropriate information. In some embodiments, a wireless signal coverage area associated with a network node 115 may be called a cell 125. In some embodiments, UEs 110 may have device-to-device (D2D) capability. In this way, UEs 110 may be able to receive signals from and / or transmit signals directly to another UE.
[0057] In certain embodiments, network nodes 115 can interface with a radio network controller. The radio network controller can control network nodes 115 and can provide certain radio resource management functions, mobility management functions and / or other suitable functions. In certain embodiments, the functions of the radio network controller can be included in network node 115. The radio network controller can interface with a core network node. In certain embodiments, the radio network controller can interface with the core network node via an interconnect network 120. Interconnect network 120 can refer to any interconnect system with the ability to transmit audio, video, signals, data, messages or any combination thereof. Interconnection network 120 may include all or a portion of a public switched telephone network (PSTN), an
Petition 870190073105, of 07/30/2019, p. 210/269
22/50 public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional or global computer or communication network, such such as the Internet, a wired or wireless network, a company intranet or any other suitable communication link, including combinations thereof.
[0058] In some modalities, the core network node can manage the establishment of communication sessions and various other functionalities for UEs 110. UEs 110 can exchange certain signals with the core network node using the layer of communication layer. not access. In the non-access layer signaling, the signals between the UEs 110 and the core network node can be passed, transparently, through the radio access network. In certain embodiments, network nodes 115 can interface with one or more network nodes through an interface between nodes, such as, for example, an X2 interface.
[0059] As described above, the exemplary modalities of network 100 may include one or more wireless devices 110, and one or more different types of network nodes with the ability to communicate (directly or indirectly) with wireless devices 110.
[0060] In some embodiments, the term non-limiting EU is used. The UEs 110, described in this document, can be any type of wireless device with the ability to communicate with network nodes 115 or another UE through radio signals. The UE 110 can also be a radio communication device, target device, D2D UE, machine-type communication UE or EU with machine-to-machine (M2M) communication capability, low cost and / or low complexity UE, a sensor equipped with EU, Tablet, mobile terminals, smart phone, equipment built into laptop
Petition 870190073105, of 07/30/2019, p. 211/269
23/50 (LEE), laptop-mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc. The UE 110 can operate either under normal coverage or enhanced coverage over its server cell. Enhanced coverage can alternatively be called extended coverage. The UE 110 can also operate at a plurality of coverage levels (for example, normal coverage, enhanced coverage level 1, enhanced coverage level 2, enhanced coverage level 3 and so on). In some cases, the UE 110 can also operate in out-of-coverage scenarios.
[0061] In addition, in some modalities, the generic terminology, radio network node (or simply network node) is used. The same can be any type of network node, which can comprise a base station (BS), base station, Node B, multi-standard radio radio node (MSR), such as MSR BS, evolved Node B (eNB ), NR gNB, network controller, radio network controller (RNC), base station controller (BSC), relay node, relay donor node controlling relay, base transceiver station (BTS), access point (AP) ), radio access point, transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Header (RRH), nodes in distributed antenna system (DAS), Multicast / Multicell Coordination Entity (MCE), core network node (for example, MSC, MME, etc.), O&M, OSS, SON, positioning node (for example, E-SMLC), MDT, or any other suitable network node.
[0062] Terminologies, such as network node and UE, must be considered non-limiting and do not imply, in particular, a certain hierarchical relationship between the two; in general, gNóB can be considered as device 1 and UE, device 2, and these two devices communicate with each other through some radio channel.
Petition 870190073105, of 07/30/2019, p. 212/269
24/50 [0063] The exemplary modalities of the UE 110, network nodes 115 and other network nodes (such as radio network controller or core network node) are described in more detail below in relation to Figures 13 to 20.
[0064] Although Figure 12 illustrates a particular arrangement of network 100, the present invention contemplates that the various modalities described in this document can be applied to a variety of networks that have any suitable configuration. For example, network 100 can include any suitable number of UEs 110 and network nodes 115, as well as any additional elements suitable to support communication between the UEs or between a UE and another communication device (such as a landline). In addition, while certain modalities can be described as deployed in a Long Term Evolution (LTE) network, the modalities can be deployed in any appropriate type of telecommunication system that supports any suitable communication standards (including 5G, NR standards) and with the use of any suitable components, and are applicable to any radio access technology (RAT) or multiple RAT systems in which a UE receives and / or transmits signals (for example, data). For example, the various modalities described in this document may be applicable to Next Generation New Radio (NR) Access Technology, LTE, LTE-Advanced, 5G, UMTS, HSPA, GSM, cdma2000, WCDMA, WiMax, UMB, WiFi, other suitable radio access technology or any suitable combination of one or more radio access technologies. Although certain modalities can be described in the context of wireless transmissions on the downlink, the present invention contemplates that the various modalities are equally applicable on the uplink.
Network Node Communication without Relocating EU Context
Petition 870190073105, of 07/30/2019, p. 213/269
25/50 [0065] Figures 13 to 15 describe exemplary modalities in which a UE 110 can communicate with a new (eg target) gNB without reallocating the UE 110 context of an old gNB (eg source), while still ensuring security.
[0066] Figure 13 illustrates an exemplary RRCConnectionResume due to the periodic RAN area update in a new gNB without context relocation, according to certain modalities. More particularly, Figure 13 shows a signaling diagram for the case of a periodic RAN area update on a new gNB within the old RAN area. In the example in Figure 13, the UE 110 is initially in the RRC INACTIVE state. During or after an RAN area update timer expires, the UE 110, in step 1, sends an RA preamble to a new gNB. In step 2, the new gNB sends a RAR message to UE 110. In step 3, UE 110 sends an RRCConnectionResumeRequest message (resumeld, causeValue = ranNotificationAreaUpdateRequest) to the new gNB. In certain modalities, when the new gNB receives the RRCConnectionResumeRequest message, it sends the RRCConnectionResumeRequest directly to the old gNB (step 3). The new gNB can forward the message to the old gNB based on the resumelD that UE 110 provided in the RRCConnectionResumeRequest message.
[0067] According to an exemplary modality, the RRCConnectionResumeRequest message includes a security token (for example, Short-MAC-I) calculated using an old security key (for example, used by UE 110 in the old cell ) as well as other parameters, such as a target cell ID / frequency band. The old gNB can
Petition 870190073105, of 07/30/2019, p. 214/269
26/50 check the security token to ensure that the message is from the correct UE 110.
[0068] According to another exemplary modality, the RRCConnectionResumeRequest can have integrity protected with the use of the old security key (for example, with the use of PDCP integrity protection (PDCP Medium Access Control (MAC)). The old gNB checks the integrity of the message.
[0069] According to another exemplary modality, the RRCConnectionResumeRequest has integrity protected with the use of a new security key (for example, with the use of PDCP integrity protection (MAC PDCP)). The new security key can be derived by UE 110 in the new cell (for example, based on the old key, plus additional parameters). The old gNB can also derive the new key and use it to verify the integrity of the message.
[0070] At this stage, the old gNB verified that it is the correct UE 110 that sends the resumption request. As a result, in step 4, the old gNB will generate an RRC response message (for example, RRCConnectionSuspend) that can be protected and / or encrypted using the old or new key. The message will be forwarded, transparently, to the UE 110 through the new gNB (step 4). The message may also include assignment of a new resumelD (still pointing to the old gNB) and additional parameters, such as, new security parameter (for example, NCC) or RAN area assignment.
[0071] Figure 14 illustrates an example of small data transmission in RRC INACTIVE without relocation of EU 110 context, according to certain modalities. In the example in Figure 14, the UE 110 is
Petition 870190073105, of 07/30/2019, p. 215/269
27/50 initially in RRC INACTIVE state. Small data can refer to the communication of small data loads (for example, machine-type communication data (MTC)) on network 100 or any other suitable data. Small uplink data (UL) arrives at UE 110. In step 1, UE 110 sends an RA preamble to the new gNB. In step 2, the new gNB sends a RAR message to the UE 110.
[0072] In step 3, UE 110 sends an RRCConnectionResumeRequest (resumeld, causeValue = smallData, ULData) to the new gNB. In the example in Figure 14, the UE 110 triggers the resumption by transmitting small data and can include some small data in Msg.3 or in conjunction with Msg.3, as in subsequent transmissions after message 3. When the new gNB receives the RRCConnectionResumeRequest, it sends the RRCConnectionResumeRequest (including all parameters and UL data) directly to the old gNB (in step 4) as part of a recovery UE context request or other message. The new gNB will forward the message to the old gNB based on the summary that UE 110 provided in RRCConnectionResumeRequest.
[0073] According to an exemplary modality, the RRCConnectionResumeRequest contains a security token (for example, Short-MAC-I) calculated using the old security key (used by UE 110 in the old cell) as well as other parameters, such as a target cell / frequency band ID. The old gNB checks the security token to ensure that the message is from the correct UE 110.
[0074] According to another exemplary modality, RRCConnectionResumeRequest has integrity protected with the use of the old security key (for example, with the use of data integrity protection)
Petition 870190073105, of 07/30/2019, p. 216/269
28/50
PDCP (PDCP MAC)). The old gNB checks the integrity of the message.
[0075] According to another exemplary modality, the RRCConnectionResumeRequest has integrity protected with the use of a new security key (for example, with the use of PDCP integrity protection (MAC PDCP)). The new security key can be derived by UE 110 in the new cell (for example, based on the old key, plus additional parameters). The old gNB also derives the new key and uses it to verify the integrity of the message.
[0076] At this stage, the old gNB verified that it is the correct UE 110 that sends the resumption request. As a result, the old gNB will forward the UE context to the new gNB and optionally include a UL Data CONF (step 5). In addition, the old gNB can forward UL data to the Core Network (5G). The UE context, sent to the new gNB, may contain information, such as the new UE security key and / or the new UE Resume ID to be assigned to the UE 110. The old gNB will also store the context. Once the new gNB receives the context, it can generate an RRC message (for example, RRCConnectionSuspend) that can be sent to UE 110 with the optional UL data CONF. The RRC message can be encrypted and / or have integrity protected using the PDCP protocol. The RRC message can contain a new resume ID, new security parameter (for example, NCC) and / or RAN area assignment. After the new gNB sends the information to the UE 110 (and possibly received confirmation from the UE 110), the new gNB can exclude the UE context locally.
[0077] In the exemplary modalities described above, thanks to the possibility to assign UE 110 a Resume ID that is pointing
Petition 870190073105, of 07/30/2019, p. 217/269
29/50 for the old gNB, it is possible to maintain the context in the old gNB, since all subsequent data or signaling will be forwarded to the old gNB. This minimizes signaling, thereby reducing network congestion.
[0078] Additionally, the modality makes it possible to change the security keys for UE transactions. This has several benefits. For example, the use of new keys for each transaction can advantageously avoid the need to maintain the PDCP sequence number when the UE 110 is in the RRC INACTIVE state, since all PDCP SNs can be set to 0 for one new key. If the old key is used, then SNs need to be maintained to protect against reproduction protection. As another example, the use of new keys makes it possible to reallocate the context when desirable (choice of network) since this can be done without giving old keys access to the new node (which should be avoided for security reasons). As another example, the use of new keys makes it possible to pre-populate the UE context in several RAN nodes to speed up signaling, as old keys do not need to be exposed.
[0079] Figure 15 illustrates an exemplary state transition from RRC INACTIVE to RRC CONNECTED without relocation of context for small data transmission, according to certain modalities. In the example in Figure 15, UE 110 is initially in the RRCINACTIVE state. Small UL data arrives. In step 1, UE 110 sends an RA preamble to the new gNB. In step 2, the new gNB sends a RAR message to UE 110. In step 3, UE 110 sends an RRCConnectionResumeRequest (resumeld, causeValue = smallData) to the new gNB.
[0080] In the example in Figure 15, the UE 110 resumes its connection in a
Petition 870190073105, of 07/30/2019, p. 218/269
30/50 new gNB with a smallData causeValue flag. Alternatively, the causeValue flag can be mo-signaling to indicate that the UE 110 performs a Tracking Area Update.
[0081] When the new gNB receives the RRCConnectionResumeRequest with the indication of small data, in step 4, it sends a recovery UE context request message to the old gNB (located using the resumeld) and includes the indicator small data. In some modalities, the indication of small data can be sent together with the Connection Resume Request. For illustrative purposes, two alternatives to responding to this message are described. According to a first exemplary modality, the old gNB responds with a recovery UE context response and the UE context includes the parameters necessary to suspend UE 110 (resumeld, RanArealnformation, NCC). According to a second exemplary embodiment, the old gNB responds with a recovery UE context response with only the UE context.
[0082] In both the first and second exemplary modalities above, the new gNB creates a local copy of UE context and sends an RRCConnectionResume message to UE 110, in step 6. The RRCConnectionResume message transitions UE 110 to RRCCONNECTED state.
[0083] In step 7, UE 110 responds with an RRCConnectionResumeComplete, which can include UL data, which is then forwarded to the old gNB in step 8. Depending on configurations, UE 110 can send some subsequent data transmissions which are all sent to the old gNB. This is shown in step 9 in the example in Figure
Petition 870190073105, of 07/30/2019, p. 219/269
31/50
15.
[0084] When the UE 110 is finished transmitting small data, it can indicate this in a variety of ways. As an example, the UE 110 can indicate this through a buffer status report, sent before the first transmission, between data or after the last message that indicates to the network the amount of data that the UE 110 wants to send. As another example, the UE 110 can indicate this through a data marker end indicating that the UE 110 has completed the transmission of small data. As yet another example, the UE 110 can indicate this through a pre-configured size of the small data - if the standardization determines that small data only amounts to a fixed number of maximum UL transmissions.
[0085] When UE 110 has completed UL traffic, the new gNB may decide to suspend UE 110. This is shown in the example in Figure 15, in step
11. In the first example mode above, when the new gNB receives the settings for the new RAN area and new resumeld, the new gNB indicates to the old gNB that the small data transmission is complete. In the second exemplary embodiment above, the old gNB responds to this message with a UE suspension response that includes this information, shown in the example in Figure 15, in step 13. After that, in step 14 the new gNB suspends UE 110 with a resumeld that points to the old gNB. As a last step, the new gNB excludes the UE context in step 15, and the UE context is stored in the old gNB. UE 110 enters RRCJNACTIVE state.
[0086] In certain modalities, the different steps in the various modalities described above can be combined to create new
Petition 870190073105, of 07/30/2019, p. 220/269
32/50 modalities. In addition, the various modalities described above can be enhanced with the innovative UE functionality below. In certain modalities, the UE 110 can indicate to the network (for example, in the RRCConnectionResumeRequest) if the procedure should be executed without performing a context search. This information may have been provided to the UE 110 in the RRCConnectionSuspend message (or other message). This will allow the new gNB to know which procedure to apply, which can advantageously lead to more efficient manipulation.
[0087] In certain modalities, the UE 110 may indicate a counter or validity information related to the UE context. This can allow the new gNB to determine whether a local context of UE 110 is still valid, which can advantageously lead to more efficient manipulation (no context search). The local context of UE 110 can be a context used in previous access, or a pre-populated context. The UE 110 can either calculate and maintain counter or expiration information or the information can be provided to the UE 110 at RRCConnectionSuspend.
[0088] In certain modalities, the UE 110 can indicate the amount of data it has in its buffer, which can advantageously allow the new gNB or the old gNB to decide whether the UE context should be relocated or not. Small amounts of data can be better served by maintaining the context, while if a lot of data is sent, it may be better to reallocate it to the optimized data routing path on the network.
[0089] In certain modalities, the UE 110 can derive different security keys depending on which node the UE 110 is connected to (or which cell). This can advantageously guarantee that different keys are
Petition 870190073105, of 07/30/2019, p. 221/269
33/50 generated for different nodes, which increases the security of the system.
Exemplary network component descriptions [0090] Figure 16 is a block diagram of an exemplary wireless device 110, according to certain modalities. Wireless device 110 can refer to any type of wireless device that communicates with a node and / or another wireless device in a cellular or mobile communication system. Examples of the wireless device 110 include a mobile phone, a smart phone, a PDA (Personal Digital Assistant), a portable computer (for example, laptop, tablet), a sensor, an actuator, a modem, a communication device of the type machine (MTC) / machine to machine device (M2M), laptop-built equipment (LEE), laptop-mounted equipment (LME), USB dongles, a D2D-capable device, or other device that can provide wireless communication. A wireless device 110 can also be called UE 110, a station (STA), a device or a terminal, in some embodiments. Wireless device 110 includes transceiver 1610, processing circuitry 1620 and memory 1630. In some embodiments, transceiver 1610 facilitates wireless signal transmission to and receipt of wireless signals from network node 115 ( for example, via an antenna), the processing circuitry 1620 executes instructions to provide some or all of the functionality described above as being provided by wireless device 110, and memory 1630 stores the instructions executed by the circuitry 1620 processing speed.
[0091] 1620 processing circuitry may include any suitable combination of hardware and software deployed in one or more modules to execute instructions and manipulate data to perform
Petition 870190073105, of 07/30/2019, p. 222/269
34/50 some or all of the described functions of the wireless device 110, such as the functions of the wireless device 110 described above in connection with Figures 1 to 15. In some embodiments, the 1620 processing circuitry may include, for example , one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more applications, one or more application specific integrated circuits (ASICs), one or more field programmable port arrangements (FPGAs) ) and / or other logic.
[0092] 1630 memory is operable, in general, to store instructions, such as a computer program, software, an application that includes one or more among logic, rules, algorithms, code, tables, etc. and / or other instructions capable of being executed by the 1620 processing circuitry. Examples of 1630 memory include computer memory (for example, Random Access Memory (RAM) or Read-Only Memory (ROM)), media mass storage (for example, a hard drive), removable storage media (for example, a Compact Disc (CD) or Digital Video Disc (DVD)) and / or any other volatile or non-volatile memory devices, transient, computer readable and / or computer executable that store information, data and / or instructions that can be used by the 1620 processing circuitry.
[0093] Other modalities of wireless device 110 may include additional components in addition to those shown in Figure 16 that may be responsible for providing certain aspects of wireless device functionality, including any of the functionality described above and / or any additional functionality ( including any
Petition 870190073105, of 07/30/2019, p. 223/269
35/50 functionality required to support the solution described above). As an example only, wireless device 110 may include input circuits and devices, output devices and one or more synchronization circuits or units, which may be part of the 1620 processing circuitry. Input devices include mechanisms for inserting data into a wireless device 110. For example, input devices may include input mechanisms, such as a microphone, input elements, a display, etc. Output devices may include mechanisms for outputting data in audio, video and / or hard copy format. For example, output devices can include a speaker, a display, etc.
[0094] Figure 17 is a block diagram of an exemplary network node 115, according to certain modalities. Network node 115 can be any type of radio network node or any network node that communicates with a UE and / or with another network node. Examples of network node 115 include an eNodeB, gNB, a B node, a base station, a wireless access point (for example, a Wi-Fi access point), a low power node, a transceiver station base (BTS), relay, donor node controlling relay, transmission points, transmission nodes, remote RF unit (RRU), remote radio header (RRH), multi-standard radio radio node (MSR), such as MSR BS, nodes in distributed antenna system (DAS), O&M, OSS, SON, positioning node (for example, E-SMLC), MDT or any other suitable network node. Network nodes 115 can be implemented over network 100 as a homogeneous implementation, heterogeneous implementation or mixed implementation. A homogeneous implementation can generally describe an implementation consisting of the
Petition 870190073105, of 07/30/2019, p. 224/269
36/50 same type (or similar) of network nodes 115 and / or similar coverage and cell sizes and inter-site distances. A heterogeneous implementation can generally describe implementations using a variety of types of network nodes 115 that have different cell sizes, transmission powers, capacities and inter-site distances. For example, a heterogeneous implementation can include a plurality of low power nodes placed along a macrocell layout. Mixed implementations can include a mixture of homogeneous portions and heterogeneous portions.
[0095] Network node 115 may include one or more of 1710 transceivers, 1720 processing circuitry, 1730 memory and 1740 network interface. In some embodiments, the 1710 transceiver facilitates wireless signal transmission to and reception of wireless signals from wireless device 110 (for example, via antenna 1750), the 1720 processing circuitry executes instructions to provide some or all of the functionality described above as being provided by a network node 115, the 1730 memory stores the instructions executed by the 1720 processing circuitry, and the 1740 network interface communicates signals with backend network components, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), network nodes. core network or radio network controllers 130, etc.
[0096] The 1720 processing circuitry may include any suitable combination of hardware and software deployed in one or more modules to execute instructions and manipulate data to perform some or all of the described functions of network node 115, such as those described above in relation to Figures 1 to 15. In some embodiments, the
Petition 870190073105, of 07/30/2019, p. 225/269
The processing circuit set 1720 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more applications and / or other logic.
[0097] The 1730 memory is generally operable to store instructions, such as a computer program, software, an application that includes one or more among logic, rules, algorithms, code, tables, etc. and / or other instructions capable of being executed by the 1720 processing circuitry. Examples of 1730 memory include computer memory (for example, Random Access Memory (RAM) or Read-Only Memory (ROM)), media mass storage (for example, a hard drive), removable storage media (for example, a Compact Disc (CD) or Digital Video Disc (DVD)) and / or any other volatile or non-volatile memory devices, transient, computer readable and / or computer executable that store information.
[0098] In some embodiments, the 1740 network interface is communicatively coupled to the 1720 processing circuitry and can refer to any suitable operable device to receive input to network node 115, send output from the network node 115, perform proper processing of the input or output or both, communicate with other devices, or any combination thereof. The 1740 network interface can include appropriate hardware (for example, port, modem, network interface card, etc.) and software, which includes data processing and protocol conversion capabilities, to communicate over a network.
[0099] Other modalities of network node 115 may include additional components in addition to those shown in Figure 17 that may be responsible for providing certain aspects of network node functionality.
Petition 870190073105, of 07/30/2019, p. 226/269
38/50 radio network, including any of the functionality described above and / or any additional functionality (including any functionality required to support the solutions described above). The various different types of network nodes may include components that have the same physical hardware, but are configured (for example, programmatically) to support different radio access technologies, or may represent partially or totally different physical components.
[00100] Figure 18 is a block diagram of a radio network controller or exemplary core network node 130, according to certain modalities. Examples of network nodes may include a mobile switching center (MSC), a GPRS server support node (SGSN), a mobility management entity (MME), a radio network controller (RNC), a radio controller base station (BSC), and so on. The radio network controller or core network node 130 includes processing circuitry 1820, memory 1830, and network interface 1840. In some embodiments, processing circuitry 1820 executes instructions to provide some or all of the features described above as being provided by the network node, memory 1830 stores the instructions executed by the processing circuitry 1820, and the network interface 1840 communicates signals with any suitable node, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), network nodes 115, radio network controllers or core network nodes 130, etc.
[00101] The 1820 processing circuitry may include any suitable combination of hardware and software deployed in one or more modules to execute instructions and manipulate data to perform
Petition 870190073105, of 07/30/2019, p. 227/269
39/50 some or all of the described functions of the radio network controller or core network node 130. In some embodiments, the processing circuitry 1820 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more applications and / or other logic.
[00102] The 1830 memory is operable, in general, to store instructions, such as a computer program, software, an application that includes one or more among logic, rules, algorithms, code, tables, etc. and / or other instructions capable of being executed by the 1820 processing circuitry. Examples of 1830 memory include computer memory (for example, Random Access Memory (RAM) or Read-Only Memory (ROM)), media mass storage (for example, a hard drive), removable storage media (for example, a Compact Disc (CD) or Digital Video Disc (DVD)) and / or any other volatile or non-volatile memory devices, transient, computer readable and / or computer executable that store information.
[00103] In some modalities, the 1840 network interface is communicatively coupled to the 1820 processing circuitry and can refer to any suitable operable device to receive input to the network node, send output from the node network, perform proper input or output processing or both, communicate with other devices, or any combination of them. The 1840 network interface can include appropriate hardware (for example, port, modem, network interface card, etc.) and software, which includes data processing and protocol conversion capabilities, to communicate over a network.
[00104] Other modalities of the network node may include components
Petition 870190073105, of 07/30/2019, p. 228/269
40/50 additional to those shown in Figure 18 that may be responsible for providing certain aspects of network node functionality, including any functionality described above and / or any additional functionality (which includes any functionality required to support the solution described above).
[00105] Figure 19 is a schematic block diagram of an exemplary wireless device, according to certain modalities. Wireless device 110 may include one or more modules. For example, wireless device 110 may include a 1910 determination module, a 1920 communication module, a 1930 receiving module, a 1940 input module, a 1950 display module and any other suitable modules. In some embodiments, one or more of the 1910 determination module, the 1920 communication module, the 1930 receiving module, the 1940 input module, the 1950 display module or any other suitable module can be deployed using a or more processors, such as the 1620 processing circuitry described above in relation to Figure 16. In certain embodiments, the functions of two or more among the various modules can be combined into a single module. The wireless device 110 can perform the methods for resuming RRC without searching for context, described above in relation to Figures 1 to 15.
[00106] The 1910 determination module can perform the processing functions of the wireless device 110. The 1910 determination module can include or be included in one or more processors, such as the 1620 processing circuitry, described above in relation to to Figure 16. The 1910 determination module can include circuitry
Petition 870190073105, of 07/30/2019, p. 229/269
41/50 analog and / or digital configured to perform any of the functions of the 1910 determination module and / or 1620 processing circuit set described above. The functions of the 1910 determination module, described above, can be performed, in certain modalities, in one or more distinct modules.
[00107] Communication module 1920 can perform the transmission functions of wireless device 110. As an example, communication module 1930 can send a request to resume connection to a first network node (for example, a new network node) network), the connection resume request including a resume ID associated with a second network node (for example, an old network node). The communication module 1920 can include a transmitter and / or a transceiver, such as transceiver 1610, described above in relation to Figure 16. The communication module 1920 can include circuitry configured to wirelessly transmit messages and / or signs. In particular modalities, the communication module 1920 can receive messages and / or signals for transmission from the determination module 1910. In certain modalities, the functions of the communication module 1920, described above, can be performed in one or more distinct modules .
[00108] The receiving module 1930 can perform the receiving functions of the wireless device 110. For example, the receiving module 1930 can receive an RRC response message from the second network node that is transparently forwarded to the wireless device through the first network node. According to another example, the receiving module 1930 can obtain the resume identification associated with the second network node.
Petition 870190073105, of 07/30/2019, p. 230/269
42/50 [00109] The 1930 receiving module may include a receiver and / or a transceiver. The receiving module 1930 may include a receiver and / or a transceiver, such as transceiver 1610, described above in relation to Figure 16. The receiving module 1930 may include circuitry configured to receive messages and messages wirelessly. / or signs. In particular modalities, the receiving module 1930 can communicate messages and / or signals received with the determination module 1910. The functions of the receiving module 1930, described above can be performed, in certain modalities, in one or more distinct modules.
[00110] The 1940 input module can receive user input for wireless device 110. For example, the input module can receive key presses, button presses, touches, slips, audio signals, video signals and / or any other appropriate signs. The input module may include one or more keys, buttons, levers, switches, switches, touch screens, microphones and / or cameras. The input module can communicate signals received with the 1910 determination module. The functions of the 1940 input module, described above, can be performed, in certain modalities, in one or more different modules.
[00111] 1950 display module can display signals on a display of wireless device 110. The 1950 display module can include the display and / or any set of appropriate circuits and hardware configured to display signals on the display. The 1950 display module can receive signals to display on the display from the 1910 determination module. The functions of the 1950 display module described above can be performed, in certain modalities, on one or more different modules.
Petition 870190073105, of 07/30/2019, p. 231/269
43/50 [00112] The 1910 determination module, the 1920 communication module, the 1930 receiving module, the 1940 input module and the 1950 display module can include any suitable hardware and / or software configuration. Wireless device 110 may include additional modules in addition to those shown in Figure 19 that may be responsible for providing any suitable functionality, including any of the functionality described above and / or any additional functionality (including any functionality required to support the various solutions described in this document).
[00113] Figure 20 is a schematic block diagram of an exemplary network node 115, according to certain modalities. Network node 115 may include one or more modules. For example, network node 115 may include the determination module 2010, the communication module 2020, the receiving module 2030 and any other suitable modules. In some embodiments, one or more of the determination module 2010, the communication module 2020, the receiving module 2030 or any other suitable module can be deployed using one or more processors, such as the set of processing circuits 1720, described above in relation to Figure 17. In certain modalities, the functions of two or more among the various modules can be combined into a single module. Network node 115 can perform the methods for resuming RRC without searching for context, described above in relation to Figures 1 to 15.
[00114] The determination module 2010 can perform the functions of processing node 115. In certain modalities, the node 115 can perform the functions of the first node (or new gNB) described in this document. In such a scenario, the 2010 determination module
Petition 870190073105, of 07/30/2019, p. 232/269
44/50 can create a local UE context and release the local UE context after suspending the wireless device. In certain embodiments, network node 115 can perform the functions of the second network node (or old gNB) described in this document. In such a scenario, the 2010 determination module checks the request to resume connection. As another example, the 2010 determination module can generate an RRC response message for the wireless device. In yet another example, the 2010 determination module can assign a resume ID to the wireless device, the resume ID associated with the second network node.
[00115] Determination module 2010 can include or be included in one or more processors, such as the 1720 processing circuit set, described above in relation to Figure 17. The 2010 determination module can include analog and / or circuit set digital configured to perform any of the functions of the 2010 determination module and / or 1720 processing circuit set described above. The functions of the 2010 determination module can be performed, in certain modalities, in one or more distinct modules.
[00116] Communication module 2020 can perform the transmission functions of network node 115. In certain modalities, network node 115 can perform the functions of the first network node (or new gNB) described in this document. In such a scenario, communication module 2020 can send the request to resume connection to the second network node associated with the resume identification based on the resume identification included in the resume request. As another example, the communication module 2020 can forward an RRC response message from the second network node to the wireless device. As yet another
Petition 870190073105, of 07/30/2019, p. 233/269
45/50 example, the communication module 2020 may send the request to resume connection to the second network node as part of a UE Recovery context request or other message. In some modalities, the communication module 2020 can send the request to resume connection to the second network node in conjunction with a UE Recovery context request or other message.
[00117] In certain embodiments, network node 115 can perform the functions of the second network node (or old gNB). In such a scenario, the 2020 communication module can send the RRC response message to the wireless device via the first network node. As another example, the communication module 2020 can send a UE context response to the first network node.
[00118] Communication module 2020 can transmit messages to one or more of the wireless devices 110. Communication module 2020 can include a transmitter and / or a transceiver, such as the 1710 transceiver, described above in relation to Figure 17. The communication module 2020 may include a set of circuits configured to transmit messages and / or signals wirelessly. In particular modalities, the communication module 2020 can receive messages and / or signals for transmission from the determination module 2010 or any other module. The functions of the 2020 communication module can be carried out, in certain modalities, in one or more distinct modules.
[00119] Receiving module 2030 can perform the receiving functions of network node 115. In certain modalities, network node 115 can perform the functions of the first network node (or new gNB) described in this document. In such a scenario, the 2030 receiving module can
Petition 870190073105, of 07/30/2019, p. 234/269
46/50 receive a request to resume connection from a wireless device, and the request to resume connection includes a resume ID associated with a second network node. As another example, the receiving module 2030 can receive a UE context response from the second network node.
[00120] In certain embodiments, network node 115 can perform the functions of the second network node (or old gNB). In such a scenario, the 2030 receiving module may receive a request to resume connection to a wireless device from a first network node, the request to resume connection including a resume identification associated with the second network node. As another example, the 2030 receiving module can receive the request to resume connection from the first network node as part of a Recovery UE context request or other message. In some embodiments, the 2030 receiving module may receive the request to resume connection from the first network node in conjunction with a Recovery EU Context request or other message.
[00121] Receiving module 2030 can receive any appropriate information from a wireless device. Receiving module 2030 may include a receiver and / or a transceiver, such as transceiver 1710, described above in relation to Figure 17. The receiving module 2030 may include circuitry configured to receive messages and / wirelessly or signs. In particular modalities, the receiving module 2030 can communicate messages and / or signals received with the determination module 2010 or any other suitable module. The functions of the 2030 receiving module can be performed, in
Petition 870190073105, of 07/30/2019, p. 235/269
47/50 certain modalities, in one or more distinct modules.
[00122] The determination module 2010, the communication module 2020 and the receiving module 2030 can include any suitable hardware and / or software configuration. Network node 115 may include additional modules in addition to those shown in Figure 20 that may be responsible for providing any suitable functionality, including any of the functionality described above and / or any additional functionality (including any functionality required to support the various solutions described in this document).
[00123] Modifications, additions or omissions can be made to the systems and devices described in this document without departing from the scope of the invention. The components of the systems and devices can be integrated or separated. In addition, the operations of the systems and devices can be performed by more, less or other components. Additionally, the operations of the systems and devices can be carried out using any suitable logic that includes software, hardware and / or other logic. As used in this document, each refers to each member of a set or each member of a subset of a set.
[00124] Modifications, additions or omissions can be made to the methods described in this document without departing from the scope of the invention. The methods may include more, less or other steps. Additionally, the steps can be performed in any appropriate order.
[00125] Although this invention has been described in terms of certain modalities, changes and permutations of the modalities will be evident to those skilled in the art. Consequently, the above description of the modalities does not restrict this invention. Other changes, replacements and
Petition 870190073105, of 07/30/2019, p. 236/269
48/50 changes are possible without departing from the spirit and scope of this invention, as defined by the following claims.
Abbreviations used in the preceding description include:
Abbreviation description 3GPP Third Generation Partnership Project AP Access point AT Access Stratum BS Base Station BSC Base Station Controller BTS Base Transceiver Station CN Core network CPE Customer Premise Equipment D2D Device to Device DAS Distributed Antenna System DCI Downlink Control Information DL Downlink eNB Evolved node B EPC Evolved Pack Core FDD Frequency Division Duplex LAN Local Area Network LEE Laptop Embedded Equipment LME Laptop Mounted Equipment LTE Long Term Evolution M2M Machine to Machine MAN Metropolitan Area Network MCE Dissemination Coordination Entity
Petition 870190073105, of 07/30/2019, p. 237/269
49/50 selective / Mu Iticélu la
M CS Modulation and coding level scheme MSR Multipattern Radio NAS Non-Access Stratum NR New Radio OFDM Orthogonal Frequency Division Multiplexing PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PSTN Public Switched Telephone Network PUSCH Physical Uplink Shared Channel PUCCH Physical Uplink Control Channel FROG Random Access RAR Random Access Response RAN Radio access network RB Resource Block RNC Radio Network Controller RRC Radio Resource Control RRH Remote Radio Header RRU Remote Radio Unit OK Tracking Area TAU Tracking Area Update TDD Time Division Duplex TFRE Time Resource Element Frequency UCI Uplink Control Information HUH User Equipment UL Ascending Link
Petition 870190073105, of 07/30/2019, p. 238/269
50/50
WAN
Wide Area Network

权利要求:
Claims (48)
[1]
1. Method on a target network node (115a) to communicate with user equipment (UE) (110) that was previously in communication with a source network node (115b) characterized by the fact that it comprises:
receiving a resume connection request from a UE (110), the resume connection request comprises a resume identification associated with the source network node (115b);
transmit the request to resume connection to the source network node (115b);
receiving a radio resource control (RRC) response from the source network node (115b); and forward the RRC response to the UE (110).
[2]
2. Method according to claim 1, characterized by the fact that the target network node (115a) is a gNB and the source network node (115b) is a gNB.
[3]
3. Method, according to claim 1, characterized by the fact that the request to resume connection is at least one of:
an RRCConnectionResumeRequest;
protected integrity using a security key used during previous communications with the source network node (115b); and transmitted to the source network node (115b) as part of or in conjunction with a recovery UE context request
[4]
4. Method, according to claim 1, characterized by the fact that the request to resume connection comprises a security token.
[5]
5. Method, according to claim 1, characterized by the fact that the RRC response comprises at least one of the following characteristics:
a new resume identification associated with the source network node (115b);
Petition 870190125809, of 11/29/2019, p. 9/18
2/10 a new security parameter;
an allocation of the radio access network (RAN) area; and being an RRCConnectionSuspend.
[6]
6. Method, according to claim 1, characterized by the fact that small data are transmitted as part of or in conjunction with the request to resume connection.
[7]
7. Method, according to claim 1, characterized by the fact that it also comprises:
receiving a UE context response from the source network node (115b) or creating a local UE context;
suspend the UE (110); and release the local EU context.
[8]
8. Target network node (115a) to communicate with user equipment (UE) (110) that was previously in communication with a source network node (115b), characterized by the fact that it comprises:
an interface (1710) configured to:
receiving a resume connection request from the UE (110), wherein the resume connection request comprises a resume identification associated with the source network node (115b);
processing circuitry (1720) operably coupled to the interface, the processing circuitry configured to determine that the UE (110) was previously in communication with the source network node (115b);
the interface (1710) still configured for:
transmit the request to resume connection to the source network node (115b);
Petition 870190125809, of 11/29/2019, p. 10/18
3/10 receive a radio resource control (RRC) response from the source network node (115b); and forward the RRC response to the UE (110).
[9]
9. Target network node (115a) according to claim 8, characterized in that the target network node (115a) is a gNB and the source network node (115b) is a gNB.
[10]
10. Target network node (115a), according to claim 8, characterized by the fact that the request to resume connection is at least one of an RRCConnectionResumeRequest;
protected integrity using a security key used during previous communications with the source network node (115b); and transmitted to the source network node (115b) as part of a retrieval user equipment (UE) context request.
[11]
11. Target network node (115a), according to claim 8, characterized by the fact that the request to resume connection comprises a security token.
[12]
12. Target network node (115a), according to claim 8, characterized by the fact that the RRC response comprises at least one of the following characteristics:
a new resume identification associated with the source network node (115b);
a new security parameter; and an allocation of the radio access network (RAN) area; and being an RRCConnectionSuspend.
[13]
13. Target network node (115a) according to claim 8, characterized by the fact that small data is received as part of or in conjunction with the request to resume connection.
Petition 870190125809, of 11/29/2019, p. 11/18
4/10
[14]
14. Target network node (115a) according to claim 8, characterized in that the interface (1710) is further configured to receive a UE context response from the source network node (115b).
[15]
15. Target network node (115a), according to claim 8, characterized by the fact that the set of processing circuits (1720) is further configured for:
create a local EU context;
suspend the UE (110); and release the local EU context.
[16]
16. Method on a source network node (115b) to facilitate communications between user equipment (UE) (110) and a target network node (115a), characterized by the fact that it comprises:
receiving a resume connection request to the UE (110) from the target network node (115a), the resume connection request including a resume identification associated with the source network node (115b);
verify the request to resume connection to the UE (110);
generate a radio resource control (RRC) response for the UE (110); and transmitting the RRC response to the UE (110) via the target network node (115a).
[17]
17. Method according to claim 16, characterized in that the target network node (115a) is a gNB and the source network node (115b) is a gNB.
[18]
18. Method, according to claim 16, characterized by the fact that the request to resume connection is at least one of:
an RRCConnectionResumeRequest-, and integrity protected using a security key used during previous communications with the UE (110).
Petition 870190125809, of 11/29/2019, p. 12/18
5/10
[19]
19. Method, according to claim 16, characterized by the fact that the request to resume connection comprises a security token.
[20]
20. Method according to claim 16, characterized by the fact that the RRC response comprises at least one of the following characteristics:
a new resume identification associated with the source network node (115b);
a new security parameter; and an allocation of the radio access network (RAN) area; and being an RRCConnectionSuspend.
[21]
21. Method according to claim 16, characterized by the fact that small data is received as part of or in conjunction with the request to resume connection.
[22]
22. Method according to claim 16, characterized by the fact that it further comprises receiving the request to resume connection from the target network node (115a) as part of a user equipment context request (UE) from recovery.
[23]
23. Method according to claim 16, characterized in that it further comprises transmitting a UE context response to the target network node (115a).
[24]
24. Method, according to claim 16, characterized by the fact that it further comprises assigning a resume identification to the UE (110), the resume identification associated with the source network node (115b).
[25]
25. Source network node (115b) to facilitate communications between user equipment (UE) (110) and a target network node (115a), characterized by the fact that it comprises:
an interface (1710) configured to receive a request for
Petition 870190125809, of 11/29/2019, p. 13/18
6/10 resume connection to the UE (110) from the target network node (115a), the connection resume request including a resume identification associated with the source network node (115b);
set of processing circuits (1720) operably coupled to the interface, the set of processing circuits configured for:
verify the request to resume connection to the UE (110); and generating a radio resource control (RRC) response for the UE (110); and the interface (1710) further configured to transmit the RRC response to the UE (110) via the target network node (115a).
[26]
26. Source network node (115b) according to claim 25, characterized in that the target network node (115a) is a gNB and the source network node (115b) is a gNB.
[27]
27. Source network node (115b), according to claim 25, characterized by the fact that the request to resume connection is at least one of:
an RRCConnectionResumeRequest-, and integrity protected using a security key used during previous communications with the UE (110).
[28]
28. Source network node (115b), according to claim 25, characterized by the fact that the request to resume connection comprises a security token.
[29]
29. Source network node (115b), according to claim 25, characterized by the fact that the RRC response comprises at least one of the following characteristics:
a new resume identification associated with the source network node (115b); a new security parameter;
Petition 870190125809, of 11/29/2019, p. 14/18
7/10 a radio access network (RAN) area allocation; and being an RRCConnectionSuspend.
[30]
30. Source network node (115b) according to claim 25, characterized by the fact that small data is received as part of or in conjunction with the request to resume connection.
[31]
31. Source network node (115b), according to claim 25, characterized by the fact that the interface (1710) is further configured to receive the request to resume connection from the target network node (115a) as part of or in conjunction with a recovery EU context request.
[32]
32. Source network node (115b), according to claim 25, characterized by the fact that the interface (1710) is further configured to transmit a user equipment (UE) context response to the target network node ( 115a).
[33]
33. Source network node (115b), according to claim 25, characterized by the fact that the set of processing circuits (1720) is further configured to assign a resume identification to the UE (110), the resume identification associated with the source network node (115b).
[34]
34. Method in user equipment (UE) (110) to communicate with a target network node (115a), characterized by the fact that it comprises:
transmitting a resume connection request to the target network node (115a), the resume connection request including a resume identification associated with a source network node (115b) previously communicating with the UE (110);
receive a radio resource control (RRC) response that originates from the source network node (115b) and forwarded to the UE (110) by the network node
Petition 870190125809, of 11/29/2019, p. 15/18
8/10 target (115a).
[35]
35. Method, according to claim 34, characterized by the fact that it also comprises obtaining the resume identification associated with the source network node (115b).
[36]
36. Method according to claim 34, characterized in that the target network node (115a) is a gNB and the source network node (115b) is a gNB.
[37]
37. Method according to claim 34, characterized by the fact that the RRC response comprises at least one of the following characteristics:
a new resume identification associated with the source network node (115b); a new security parameter;
an allocation of the radio access network (RAN) area; and being an RRCConnectionSuspend.
[38]
38. Method, according to claim 34, characterized by the fact that the request to resume connection is at least one of:
an RRCConnectionResumoRequest-, and integrity protected using a security key used during previous communications with the source network node (115b).
[39]
39. Method, according to claim 34, characterized by the fact that the request to resume connection comprises a security token.
[40]
40. Method, according to claim 34, characterized by the fact that small data is transmitted as part of or in conjunction with the request to resume connection.
[41]
41. User equipment (UE) (110) for communication with a target network node (115a), characterized by the fact that it comprises:
set of processing circuits (1620) configured to operate in
Petition 870190125809, of 11/29/2019, p. 16/18
9/10 an RRCJNACTIVE state; and an interface (1610) operably coupled to the processing circuitry (1620), the interface (1610) configured to:
transmitting a resume connection request to the target network node (115a), the resume connection request including a resume identification associated with a source network node (115b) previously communicating with the UE (110); and receiving a radio resource control (RRC) response that originates from the source network node (115b) and forwarded to the UE (110) by the target network node (115a).
[42]
42. UE (110), according to claim 41, characterized by the fact that the interface is further configured to obtain the resume identification associated with the source network node (115b).
[43]
43. UE (110) according to claim 41, characterized in that the target network node (115a) is a gNB and the source network node (115b) is a gNB.
[44]
44. UE (110) according to claim 41, characterized by the fact that the RRC response comprises at least one of the following characteristics:
a new resume identification associated with the source network node (115b); a new security parameter;
an allocation of the radio access network (RAN) area; and being an RRCConnectionSuspend.
[45]
45. UE (110), according to claim 41, characterized by the fact that the request to resume connection is at least one of:
an RRCConnectionResumeRequest-, and integrity protected using a security key used during previous communications with the source network node (115b).
Petition 870190125809, of 11/29/2019, p. 17/18
10/10
[46]
46. UE (110), according to claim 41, characterized by the fact that the request to resume connection comprises a security token.
[47]
47. UE (110), according to claim 41, characterized by the fact that small data is transmitted as part of or in conjunction with the request to resume connection.
[48]
48. Invention of a product, process, system, kit, means or use, characterized by the fact that it comprises one or more elements described in the present patent application.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019015723A2|2020-03-24|RESUME OF RADIO RESOURCE CONTROL WITHOUT CONTEXT SEARCH

---

JP6703145B2|2020-06-03|Operation without permission

---

US10091821B2|2018-10-02|Methods and network node for activation of connection configuration for a secondary base station

---

US20140321416A1|2014-10-30|Method and apparatus for controlling cross link establishment

---

US11039313B1|2021-06-15|Securing network steering information

---

KR20200089316A|2020-07-24|Communication method and communication device

---

JP6922997B2|2021-08-18|Wireless terminal and its method

---

US20150271783A1|2015-09-24|Paging method and device

---

BR112019024381A2|2020-06-09|uplink transmission of small data in idle state

---

JP2019518360A|2019-06-27|System and method for controlling wireless device feedback on secondary cell activation and deactivation via unlicensed spectrum

---

WO2017024890A1|2017-02-16|Device-to-device communication method, apparatus and system

---

KR20210006453A|2021-01-18|UE behavior related to rejection of resume request

---

US20190007268A1|2019-01-03|Methods and Network Node for Activation of Connection Configuration for a Secondary Base Station

---

WO2019105695A1|2019-06-06|Secure deactivation of subscriber identifier protection in 5g

---

US20220022121A1|2022-01-20|Handling of Measurement Configuration Upon Conditional Mobility Execution

---

EP3955614A1|2022-02-16|Communication method and device

---

US11252561B2|2022-02-15|Refreshing a security context for a mobile device

---

EP3915285A1|2021-12-01|Securing the user plane path for a group communication session based on a security policy common to all devices in the group

---

US11039312B2|2021-06-15|Handling of multiple authentication procedures in 5G

---

TW202143763A|2021-11-16|Signaling enhancement for dynamic power sharing in dual connectivity

---

WO2021049993A1|2021-03-18|Ue frequency selection and prioritization based on network slice information

---

WO2021154142A1|2021-08-05|Reporting failures of conditional handover mobility operations

---

BR112021014353A2|2021-09-28|HANDLING THE MEASUREMENT SETTING BY PERFORMING CONDITIONAL MOBILITY

---

WO2021101428A1|2021-05-27|Early measurement reporting of suspended secondary cell group |

---

WO2021015655A1|2021-01-28|Release, suspend and reconfiguration in paging

同族专利:

---

公开号 | 公开日

---

AU2017397009B2|2021-04-29|

---

CN110249703A|2019-09-17|

---

JP2020507971A|2020-03-12|

---

US20200037210A1|2020-01-30|

---

WO2018142207A1|2018-08-09|

---

AU2017397009A1|2019-08-01|

---

US11160132B2|2021-10-26|

---

EP3578001A1|2019-12-11|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US20100232327A1|2006-11-16|2010-09-16|Electronics And Telecommunications Research Instiu|Method for handover procedure of user terminal during power saving operation in cellular system|

---

US9144100B2|2009-08-17|2015-09-22|Google Technology Holdings LLC|Method and apparatus for radio link failure recovery|

---

EP3154307B1|2013-08-09|2018-04-11|HTC Corporation|Method and device for radio network temporary identifier allocation in dual connectivity|

---

US9924460B2|2014-10-28|2018-03-20|Telefonaktiebolaget Lm Ericcson |Network nodes, a user equipment and methods therein for handling a connection between the user equipment and a wireless communications network|

---

US9820193B2|2015-05-04|2017-11-14|Verizon Patent And Licensing Inc.|Determining a user equipment context for a radio resource control connection reestablishment request|

---

CN106900015B|2015-12-18|2021-02-12|中兴通讯股份有限公司|Method and device for processing reestablishment in cross-base-station switching process|

---

EP3383125A4|2015-12-22|2019-01-02|Huawei Technologies Co., Ltd.|Data transmission processing method, user equipment and base station|

---

JP2019501595A|2016-01-08|2019-01-17|ノキア テクノロジーズ オーユー|User plane optimization for narrowband Internet of Things|

---

CN109479230B|2016-07-21|2021-03-26|株式会社Kt|Method for performing mobility processing of NB-IoT terminal and apparatus therefor|

---

US10694444B2|2017-01-05|2020-06-23|Sharp Laboratories Of America, Inc.|UE-based expedited handoff|

---

US11026140B2|2017-01-29|2021-06-01|Lg Electronics Inc.|Method for managing terminal context and device for supporting same|CN108617033B|2017-01-26|2021-06-29|华为技术有限公司|Communication method, terminal and access network equipment|

---

CN109691179B|2017-03-22|2021-01-29|华为技术有限公司|Session migration method and device|

---

CN109246774B|2017-06-16|2021-01-05|华为技术有限公司|Communication method and device|

---

US20200053791A1|2018-08-13|2020-02-13|Qualcomm Incorporated|Downlink data transmission in rrc inactive mode|

---

SG11202008494PA|2018-08-17|2020-10-29|Guangdong Oppo Mobile Telecommunications Corp Ltd|Information transmission method and apparatus, and communication device|

---

WO2020087280A1|2018-10-30|2020-05-07|Qualcomm Incorporated|Configurations for small data transmission|

---

US11265909B2|2018-12-16|2022-03-01|Qualcomm Incorporated|Small data transfer over configured grants for asynchronous non-orthogonal multiple access|

---

WO2020191059A1|2019-03-19|2020-09-24|Apple Inc.|Signaling for inactive small data transmission without path switching|

---

CN111757556A|2019-03-29|2020-10-09|华为技术有限公司|Data transmission method and device|

---

WO2021035711A1|2019-08-30|2021-03-04|华为技术有限公司|Data transmission method and device|

---

WO2021163394A1|2020-02-13|2021-08-19|Ofinno, Llc|Small data transmission |

---

WO2021253417A1|2020-06-19|2021-12-23|Oppo广东移动通信有限公司|Data transmission method and network device|

---

WO2022015028A1|2020-07-14|2022-01-20|Samsung Electronics Co., Ltd.|Method and apparatus for handling small data transmission in rrc_inactive state in a wireless communication system|

法律状态:
2021-10-13| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762454578P| true| 2017-02-03|2017-02-03|

---

US62/454,578|2017-02-03|

---

PCT/IB2017/058444|WO2018142207A1|2017-02-03|2017-12-27|Radio resource control resume without context fetch|

---